• 专利附录
  • 专利说明
  • 权利要求
  • 类似技术
  • 同族专利
  • 引用文献
  • 法律状态
  • 优先权
    • 专利摘要:
    The present invention relates to a device management system that is capable of scheduling connected devices and people for tasks, monitoring the ability of devices to perform the scheduled task by checking in with devices based on their uses and locations , and to modify the functioning of the devices according to the tasks scheduled for the devices and their uses. In addition, the system can incorporate "dumb" devices not communicated in the task scheduling and track and manage those devices.
    公开号:BR112020003112A2
    申请号:R112020003112-7
    申请日:2018-08-16
    公开日:2020-08-11
    发明作者:Christine Koski；Ryan Heaton
    申请人:Nmetric, Llc；
    IPC主号:
    专利说明:

    [001] [001] The field of the invention is that of managing device operations in scheduling tasks that involve devices. Background
    [002] [002] The general description includes information that may be useful in understanding the present invention. It is not admitted that none of the information provided herein is prior art or relevant to the currently claimed invention, or that any publication specifically or implicitly referenced is prior art.
    [003] [003] When a company has a series of tasks that need to be completed, a manager usually allocates employees for each task. Computer scheduling systems, for example, Microsoft Outlook &, can be useful for viewing these schedules. For example, a manager can use a computer-based scheduling system to block specific times of the day for employees to perform certain tasks and assign specific employees to that task. Each employee would have a schedule of tasks to perform over each day, week and month, which could be easily viewed and organized. In order for a manager to assign specific employees to each task, however, he needs to manually track each employee's schedule and allocate each employee to the appropriate task.
    [004] [004] US 2009/0315735 to Bhavani teaches a computer system to manage the flow of patients in a hospital, where a manager can tag specific patients, medical staff and resources with RFID chips to determine where each patient,
    [005] [005] US 7,587,329 for Thompson teaches a computer system to manage a health clinic, where a manager can insert a series of attributes into a computer that a nurse on call needs to have to perform a specific task. The system then combines available nurses with these requirements with the task, in order to perform the task, and can send schedules to each nurse, informing the nurse which tasks to perform.
    [006] [006] Still, the referred systems and other systems of the prior art fail to continue guaranteeing the viability of the device for a scheduled task as the agenda develops and manages the functions of the devices, so that the devices can be used in scheduled tasks with schedule changes. Likewise, prior art systems do not provide the continued inclusion of devices with processing and communication capabilities with legacy devices or other "dumb" devices that do not.
    [007] [007] Bhavani, Thompson and all other extrinsic materials discussed here are incorporated by reference to the same extent as if each individual extrinsic material were specific and individually indicated to be incorporated by reference. When a definition or use of a term in an embedded reference is inconsistent or contrary to the definition of that term provided here, the definition of that term provided here applies and the definition of that term in the reference does not apply.
    [008] [008] Thus, there is a need for a scheduling system that provides simultaneous management of connected device functions for scheduled tasks, including output settings and functionality for those who are connected to the development, exception resolution optimized for these devices and incorporation of "dumb" devices not connected to an online scheduling system within an installation. Summary of the Invention
    [009] [009] The object of the present invention provides apparatus, systems and methods in which a machine, device or piece of equipment can be scheduled for a task, and the availability of a machine, device or piece of equipment programming for a task specific scheduled time can be monitored, so that if the device / machine is no longer suitable for the task, a replacement can be found so that the task can be performed.
    [0010] [0010] In various embodiments of the object of the present invention, a computer receives a request to schedule a task, the request including task attributes with corresponding values that are associated with the task. The request includes a pair of attributes / values for the desired time period that correspond to the desired date / time of the task. The request can also include a location attribute, which corresponds to the desired location for a task. The computer selects at least one device based on the task attribute / value pairs, including the desired time period attribute / value and the corresponding device attribute / value pairs, and at least one person for one task based on attribute / task value pairs including desired time period / attribute value and assignment pairs
    [0011] [0011] In various modalities, at check-in time, the computer can also verify that at least one person is available for a task by sending a message to a device associated with the person.
    [0012] [0012] In various modes, the computer can select backup devices that are also suitable for a requested task, and based on factors such as the number of backup devices available, their respective anticipated locations, and other factors, can adjust the check-in time for the selected device for a task according to increasing the time between the check-in time and the start of the scheduled task.
    [0013] [0013] In several ways, if the computer determines that a device has a negative sufficiency status, the computer proceeds to select a backup device for a task, which may be in time for a failed check (ie, retor - negative sufficiency status), or it can be a backup among a group of pre-selected backups at the time of scheduling the task.
    [0014] [0014] In several modalities, the computer selects an alternative time for a task based on a determined status of negative sufficiency for the device, so that the alternative time is one where the sufficiency status would be positive.
    [0015] [0015] In several modalities, the devices and the computer communicate directly through data communications between the computer and the devices and vice versa (through a communication between a device and the computer with or without retransmission). In several modalities, the computer can also check in with devices without communication and processing resources through a proxy, by locating and communicating with computing devices in the locations of the dumb devices to confirm its presence.
    [0016] [0016] In various modalities, the computer can send messages that cause the devices to change their functionality, restricting their modes of operation, such as working with capacity below full capacity or emitting less than the total production available during a task, based on a scheduled task requirement and the requirements of subsequent occurrence tasks, but previously scheduled.
    [0017] [0017] Various objects, characteristics, aspects and advantages of the inventive object will become more evident from the detailed description below of preferred modalities, together with the figures in the attached drawings in which equal numbers represent similar components.
    [0018] [0018] All publications identified herein are incorporated by reference to the same extent as if each individual publication or patent application were specifically and individually indicated to be incorporated by reference. When a definition or use of a term in an embedded reference is inconsistent or contrary to the definition of that term provided here, the definition of that term provided here applies and the definition of that term in the reference does not apply.
    [0019] [0019] The following description includes information that may be useful for understanding the present invention. It is not admitted that none of the information provided herein is prior art or relevant to the currently claimed invention, or that any publication specifically or implicitly referenced is prior art.
    [0020] [0020] In some modalities, the numbers that express quantities of ingredients, properties such as concentration, reaction conditions and so on, used to describe and claim certain modalities of the invention, must be understood as being modified in some cases by the term "about". Therefore, in some modalities, the numerical parameters established in the written description and in the appended claims are approximations that may vary depending on the desired properties that are desired by a specific modality. In some modalities, the numerical parameters must be interpreted in the light of the number of significant digits reported and applying common rounding techniques. Although the ranges and numerical parameters that establish the broad scope of some modalities of the invention are approximations, the numerical values established in the specific examples are reported as precisely as possible. The numerical values presented in some modalities of the invention may contain certain errors necessarily resulting from the standard deviation found in their respective test measurements.
    [0021] [0021] Unless the context dictates otherwise, all intervals set out in this document should be interpreted as including their end points and open intervals should be interpreted to include only commercially practical values. Likewise, all lists of values should be considered as including intermediate values, unless the context indicates otherwise.
    [0022] [0022] As used in the description here and in the following claims, the meaning of "one", "one", "o" and "a" includes plural reference, unless the context clearly indicates otherwise. In addition, as used in the description of this document, the meaning of "in" includes "in" and "inside", unless the context clearly indicates otherwise.
    [0023] [0023] The recitation of ranges of values mentioned here is only intended to serve as an abbreviated method of referring individually to each separate value that fits within the range. Unless otherwise indicated here, each individual value is incorporated into the specification as if it were recited here individually. All methods described in this document may be performed in any appropriate order, unless otherwise indicated here or clearly contradicted by the context. The use of any and all examples or exemplary language (for example, "such as") provided in connection with certain embodiments herein is intended only to further clarify the invention and does not represent a limitation on the scope of the otherwise claimed invention. No language in the specification should be interpreted as indicating any unclaimed element essential to the practice of the invention.
    [0024] [0024] The groupings of alternative elements or modalities of the present invention disclosed herein should not be interpreted as limitations. Each group member can be referred and claimed individually or in any combination with other group members or other elements found here. One or more members of a group may be included or excluded from a group for reasons of convenience and / or patentability. When any inclusion or exclusion occurs, the specification is considered to contain the modified group, thereby fulfilling the written description of all Markush groups used in the attached claims. Brief Description of Drawings
    [0025] [0025] The Figure | it is a diagrammatic overview of the system according to modalities of the object of the present invention.
    [0026] [0026] Figure 2 provides an overview of a flow chart illustrating the initial task process performed by the computer, according to the modalities of the object of the present invention.
    [0027] [0027] Figure 3 provides an overview of a flow chart illustrating the check-in process performed by the computer, according to the modalities of the object of the present invention.
    [0028] [0028] Figure 4 provides an illustrative example of a device profile, according to modalities of the object of the present invention.
    [0029] [0029] Figure 5 provides an overview of a flow chart illustrating the check-in process for non-connected devices executed by the computer, according to the modalities of the object of the present invention. Detailed Description
    [0030] [0030] Through the following discussion, numerous references will be made in relation to servers, services, interfaces, mechanisms, modules, clients, peers, portals, platforms or other systems formed from computing devices. It should be considered that the use of such terms is considered to be one or more computing devices with at least one processor (for example, ASIC, FPGA, DSP, x86, ARM, ColdFire, GPU, multi-core processors, etc.) programmed to execute software instructions stored in a non-transitory, tangible and computer-readable medium (for example, hard disk, solid state drive, RAM, flash, ROM,
    [0031] [0031] The following discussion provides many examples of the inventive object. Although each modality represents a unique combination of inventive elements, it is considered that the inventive object includes all possible combinations of the elements described. Thus, if one modality comprises elements A, Be C, and a second modality comprises elements B and D, the inventive object will also be considered to include other remaining combinations of A, B, C or D, even if not explicitly described.
    [0032] [0032] It should be considered that the techniques described provide many beneficial effects, including facilitating scheduling events and ensuring that events can be held with the machines or equipment as programmed.
    [0033] [0033] Throughout this description, references will be made to "attribution
    [0034] [0034] Figure 1 provides a schematic overview of a system 100 according to modalities of the object of the invention. System 100 includes one or more computers 110 (for example, one or more central servers). For simplicity, the central computer (s) 110 will be referred to here as a single computer 110. However, it is understood that the functions and processes of computer 110 can be performed by and / or distributed among more of a computer 110 distributed locally via a local data connection interface or distributed over greater distances via long distance connection interfaces. Computer 110 may be located in the same installation or location as one or more of the other components of system 100 or remotely in separate locations.
    [0035] [0035] Devices 120 in general are a plurality of devices that can be used to help complete various tasks in a location where system 100 is employed. Devices 120 can thus include equipment such as computing devices, general tools, specialized tools, environmental controls, etc. In a hospital setting used as an illustrative example in this document, devices 120 may include scanning equipment
    [0036] [0036] As seen in Figure 1, computer 110 is connected in communication mode to a plurality of devices 120. Communication between computer 110 and the various devices 120 can be through data communication to the devices as well equipped to do so.
    [0037] [0037] System 100 includes a device database 130 that stores a device profile 121 for a plurality of devices 120. The device profile 121 of each device 120 includes a plurality of device attributes that correspond to attributes or characteristics the device. Preferably, the device attributes for each device 120 include at least those that correspond to the ability of a device to perform its intended function. Examples of device attributes include a device power status, a device supply status, a device location, a device condition, a device maintenance status, a device category, a device manufacturer , a device replenishment program, a device model number, device permissions, a device network status, etc. The collection of attributes for a particular device can be considered to be the device profile that corresponds to the device. As will be noted by the attentive reader, not all device attributes will be required to apply to all devices.
    [0038] [0038] Devices 120 can be indexed in device database 130 according to a device identifier for each device. The device identifier can be generated and assigned by the system with the creation of a database for the device. The device identifier can be generated randomly, and / or based on one or more of a device category, a manufacturer, a model number, an individual serial number, a network address, a sequential number based on the quantity other identical devices present / owned by an installation or entity, etc.
    [0039] [0039] Device database 130 may also include, in device profile 121 of each device 120, device program data for device 120 that includes entries for tasks already scheduled or other scheduling conflicts ( for example, scheduled downtime for maintenance / repair, updates, recertification, refueling, etc.) for the specific device. The schedule can be in the form of a table, calendar, etc., with date / time entries scheduled for each of the tasks / conflicts previously scheduled.
    [0040] [0040] Figure 4 provides an illustrative example of a device profile 121.
    [0041] [0041] In various modalities, the scheduling data for each 120 device can be maintained in a central scheduling or calendar program for all 120 devices (in addition to or instead of the scheduling table or other data) schedules kept for each device 120 in device database 130), with which entries for each individual device can be referenced according to an identifier associated with the device (for example, identifier database device, manufacturer / model / serial identifier, network identifier, etc.). Thus, in the referred modalities, the system consults the central scheduling program through the device identifier when it needs information about the availability and / or scheduling of a particular device according to various functions and processes associated with the subject of the invention. .
    [0042] [0042] The power status attribute of the device corresponds to the amount of energy or charge available for a battery operated device 120. Thus, the power status attribute value corresponds to a battery level or charge level of the device. device battery.
    [0043] [0043] The provision status attribute of the device corresponds to the quantity of a finite resource dispensed or used by a device 120 that is currently accessible to the device. For example, for an anesthesia tank, the device supply attribute status value corresponds to the amount of gas in the tank.
    [0044] [0044] The device power status attribute and the device supply status attribute can be referred to as resource status attributes of a device 120. Resource status attributes are attributes that reflect a quantified characteristic or parameter of a device 120 that runs out with use, such as the amount of a supply associated with the device. Thus, the device's power status attribute and the device's delivery status attributes are examples of resource state attributes.
    [0045] [0045] The device's location attribute corresponds to the device's last reported location. The location can be within a particular structure or area (for example, within a hospital).
    [0046] [0046] The device profile of some devices, such as a battery operated device or devices that store and / or dispense a resource used in certain tasks, may include one or more device replenishment attribute (s) that correspond to a scheduled refill or refill of the device. For example, for a battery-operated device, you may have a periodic pre-scheduled time for refueling (for example, every day, once a week, etc.).
    [0047] [0047] A condition attribute of the device corresponds to the current condition of the device, such as due to wear and tear, wear, etc.
    [0048] [0048] The maintenance status attribute of the device indicates whether a device requires maintenance. This can be due to a reported malfunction or a predefined periodic or maintenance schedule (for example, diagnosis or calibration of a specific device, etc.). In various modalities, the value of the device's maintenance status attribute can be a future date or a maintenance event (for example, hours of use, scheduled date, etc.).
    [0049] [0049] The permissions attribute of the device corresponds to a function, certification or other special authorization required by a user to operate the device. This may be due to specialist manufacturer training, legal requirements, etc. In certain embodiments, the permission attributes of the device may include one or more entries by specific personnel who are authorized or certified to operate the device.
    [0050] [0050] The network status attribute of the device corresponds to the network capabilities of the particular device. Certain devices
    [0051] [0051] System 100 includes a task database 140 that stores a plurality of sets of task attributes 141, each of the sets of task attributes comprises a set of task attributes associated with a particular task. Task attributes are representative of several characteristics associated with a task. Examples of task attributes include a task name, a task identifier, a task duration, required task devices, required task personnel, and required task facilities.
    [0052] [0052] The required task device attributes can include a device category, class, or name that correspond to the particular category, class, or device name required for a task. Other device task attributes may include attributes associated with the characteristics of the devices themselves, such as those that distinguish a particular device from others used for similar purposes. This can include attributes associated with the dimensions of the device, power requirements, type of device interface, hardware configurations of the device (for example, a drill with a certain size or shape of a tip), etc.
    [0053] [0053] For certain devices represented by an attribution
    [0054] [0054] System 100 also includes a personnel database 150, including a plurality of sets of personnel attributes 151, each comprising a set of personnel attribute / value pairs associated with a person individual. Examples of personnel attributes include a name, function, specialization (s), certification (s), location, etc. As in the device database 130, the personnel database 150 can similarly include a schedule for each person in the personnel database that includes entries for tasks already scheduled or other scheduling conflicts (for example, example, delimiting a working day or service schedule, vacation time, etc.) for the particular person. The schedule can be in the form of a table, calendar, etc., with date / time entries scheduled for each of the tasks / conflicts previously scheduled.
    [0055] [0055] In the modalities where a central calendar system is used, the central calendar system can similarly store scheduling information for each person from a personal database indexed according to a person's name or another personal identifier.
    [0056] [0056] Figure 2 provides an overview of the initial task scheduling performed by computer 110.
    [0057] [0057] In step 210, computer 110 receives a request to schedule a particular task. The request includes task attributes including at least an identification of a task name or category and a desired time period attribute (for example, indicating a date / time) for a task. A request typically also includes a desired location attribute (for example, indicating a location for a task such as a particular room and other relevant location information) and can also include other attributes of selected task or inserted by a requesting user.
    [0058] [0058] Based on the request, computer 110 proceeds to select one or more device (s) related to a task in step 220 based on a match of a plurality of task attributes (including the time period attribute) desired task for a user-selected task and the duration of the task associated with the task) with the device attributes of the devices 120 (and a device scheduling table and / or device scheduling in the central calendar / scheduling program) and optionally, one or more calculated values of the device's expected readiness attribute for the task. The selection of device (s) 120 for a task in step 220 is as follows:
    [0059] [0059] In step 221, computer 110 matches task attributes with corresponding device attributes from the device profile of devices 120, such as the device type, category or class in a task attribute with devices having the type of device. correspondence, category, or class device attribute and the desired time period attribute for a task with the corresponding calendars or time tables.
    [0060] [0060] If the anticipated device attribute values are used, in step 222 computer 110 calculates the anticipated device readiness attributes for each of the devices selected in step 221 and compares it to the minimum readiness attributes corresponding device in step 223.
    [0061] [0061] Computer 110 calculates the anticipated device readiness attribute values for each of the devices in step 222 by, for each device attribute that corresponds to the minimum readiness attributes of the task device, calculating the anticipated values of the device attributes based on the current values of those device attributes and the tasks already scheduled and, as applicable, other scheduled events (eg regular maintenance, refueling or recharging, etc.) in the calendar for device 120 (such as scheduling for the device in device database 130) between the current time and the desired time period.
    [0062] [0062] Thus, for a given device 120, computer 110 starts with the current values of the device attributes that correspond to the minimum readiness attributes of the task device and, for each previously scheduled task and sequential conflict / event , chronologically starting from the present and
    [0063] [0063] In several modalities, the scheduled task will include, for each device scheduled for a task, expected usage values for the attributes of the device that have to be affected by the performance of the task. These values can be based on the historical use of the device for a task (for example, determined by analyzing many uses over time and then by means of statistical analysis of likely use for a task), or it can be manually entered by a requester of that task. For example, if a certain device dispenses a certain material for use in a procedure and, for a scheduled task, it is anticipated that a particular amount of the material will be required, the expected use value for the material is the expected amount to be needed for a task. Thus, computer 110 adjusts the device's delivery status attribute to device 120 by subtracting the expected usage value for a task.
    [0064] [0064] For certain device attributes, computer 110 can determine an expected use value based on a known a priori correlation of a device attribute and one or more attributes of the scheduled task. For example, if a scheduled task is expected to use a battery-operated device for a certain period of time based on the duration of the task, and the attributes of the device include a rate of battery power consumption for the device, the computer 110 calculates an anticipated amount of energy usage for the pre-scheduled battery, multiplying the task duration by the consumption rate. This anticipated use of battery power is the expected use value used to adjust the battery powered device's power status attribute for the pre-scheduled task. Computer 110 then adjusts the power state attribute by reducing its value by the calculated expected use value.
    [0065] [0065] For events such as scheduled refueling and recharging times scheduled for a specific device (and also for scheduled maintenance times), computer 110 similarly increases the values of the respective attributes of the device, as predicted. If programmed refills / refills are expected to fully refill / recharge the device (such as a full refill or a change from a discharged to fully charged battery, tank or receptacle from empty to full material, etc.), corresponding device attribute values are defined with the full values. For gradual refueling / recharging tasks (such as a recharged battery while connected), computer 110 calculates the appropriate change in the device's attribute value based on a known a priori replenishment / refill rate and the time allocated for the refueling / refilling task.
    [0066] [0066] Thus, computer 110 takes the output of the adjusted device attribute value from a previously scheduled task and calculates it and applies the next adjustment for the next task in chronological order, as described above, to all tasks and other events scheduled for device 120 to be processed and device attribute values adjusted to account for all scheduled tasks and events scheduled before the desired desired time period of the task's desired time period attribute. The referred final device attribute values adjusted are the values
    [0067] [0067] It should be noted that the device attribute values used adjusted by computer 110 during the step 222 process are stored and changed by computer 110 for the purposes of scheduling the task separately from the profile of the device. device in device database 130. In other words, the current values of device attributes stored by device database 130 that reflect actual current values are not adjusted.
    [0068] [0068] In step 223, computer 110 compares the anticipated device readiness attribute values to the minimum device readiness attribute values. If the anticipated device readiness attribute values reach or exceed the minimum device readiness attribute values (for some attributes, reaching or exceeding the device's minimum readiness attribute values means a value that is greater or equal to that of the minimum device readiness attribute value; for others, it can mean a value that is less than or equal to, if a lower device attribute value is used to indicate greater readiness or "readiness" for the device), computer 110 schedules device 120 for a task at a desired location at the desired time / date indicated in the desired time period attribute of a request.
    [0069] [0069] In various modalities, computer 110 is also programmed to, in step 223, determine the availability of device 120 that is selected in step 222 based on the last scheduled location and the final scheduled time of the last device's previously scheduled task before the desired date / time in the desired time period attribute and the desired location in the desired location attribute in the request. Based on the expected time to go from the location of the last scheduled task and the desired location (as based on transition times defined a priori between various points in a building, such as a hospital, an analysis of the historical data involved in the movement of the specific device across particular distances, etc., and may involve accounting for expected time adjustments between the floor, such as in an elevator, based on average walking speed and / or other factors), Computer 110 determines whether there is sufficient time for device 120 to be taken from the last scheduled task to the desired location in time for the task's start time in the request, as indicated by the desired time period attribute. This calculation can include time buffers to account for device 120 setup or setup time, delays or excessive executions on the previous task, time to disconnect or "configure" the device on the previous task, etc. If computer 110 determines that device 120 can be moved to the desired location for the requested task, computer 110 programs device 120 for the desired task.
    [0070] [0070] In several modalities, for one or more selected devices 120, the calculated values of anticipated device readiness attributes can be stored with the task entry scheduled in the task calendar and / or the schedule kept in the bank device data 130 to the device.
    [0071] [0071] If the process in steps 222-223 fails for a particular device 120, computer 110 is programmed to proceed to the next device of the same type and redo the analysis until a suitable device is found. If computer 110 passes through all devices of a particular type required by the requested task without finding a match, it reports this to a requesting user. In various modalities, computer 110 can redo the analysis of step 220 for other times, such as starting with other available times closer to the desired time period in the desired time period attributes that fit the duration for a task, and when a match is found for all necessary devices 120, it suggests the alternate time for a requesting user.
    [0072] [0072] In step 230, computer 110 selects one or more personnel based on a match between the plurality of task attributes (including the desired time period attribute) and personnel attributes (including scheduling data for each person in the personal database).
    [0073] [0073] In said illustrative process, step 230 is shown as occurring after step 220. However, it is contemplated that step 230 can be performed by computer 110 before step 220.
    [0074] [0074] In the illustrative process where step 230 occurs after step 220, computer 110 also selects one or more personnel in step 230 based on the device selected in step 220. For example, if a particular device selected in step 220 requires a certification / role / private operator having certain credentials that allow them to operate the device, so computer 110 selects the operator is selected in step 230 from those having the certification / role / credentials in the corresponding attributes in their personnel attribute sets to operate the device. In other ways, step 230 can be performed before step 220. Just as with step 220, if a failure to find personnel is determined in step 230, computer 110 is programmed to alert a requesting user. In various modalities, computer 110 executes the processes of steps 220 and 230 again using other possible periods and, when encountering one or more times when the processes of steps 220 and 230 are executed with successful matches of devices and personnel corresponding, computer 110 displays suggested or more alternative times for the requesting user.
    [0075] [0075] In various modalities, computer 110 is programmed to determine the order in which to perform steps 220 and 230 based on the total number of devices 120 in the device database that fall under a device attribute. of task required for a particular task and the total number of personnel in the personal database for one or more of the devices so that the limiting factor of the devices in relation to personnel is prioritized first. For example, if, for a particular device needed for a task, there are quantity X of devices and quantity Y of personnel operating the devices, then if X is less than (or less than or equal to) Y, the computer 110 is programmed to perform step 220 first because there are fewer devices available than personnel, so it is likely that it will be more difficult to find suitable devices for the requested task, even without taking into account the actual programming. On the other hand, if X is greater than or equal to (or just greater than) Y, computer 110 is programmed to perform step 230 first because personnel are likely to be more difficult to program than the device and because it is likely that if there is personnel available, it is likely that there will also be a device available (as unauthorized personnel are not expected to be using the devices, the authorized personnel should be the only one to take over the provision of devices, not counting inoperative maintenance devices, etc.).
    [0076] [0076] The task may have certain necessary elements that are absolutely essential for the task, without which the task may
    [0077] [0077] In step 240, once all devices and personnel have been selected for the task at the desired task time (or alternate task time, if necessary), computer 110 schedules the task in a scheduling program or calendar (which can be the same discussed with respect to certain various modalities of the device and personal attribute sets, or a separate scheduling / calendar program) and updates the device and personnel information to block the scheduled task at the appropriate time. The "block" can also include additional time before and after the scheduled task to allow for travel times and provide a general buffer against possible scheduling conflicts.
    [0078] [0078] Also, in several modalities, computer 110 sends a confirmation message to device 120. The confirmation message can include an authorization for use for the task time, starting at the task start time (or in a period pre-defined before the task to allow configuration and initialization of the device as needed). Usage authorization can include login credentials for a task for the device and executable instructions that make the device rave or otherwise inaccessible for the duration of the task if the login credentials are not used.
    [0079] [0079] In several embodiments, the confirmation message may also include usage restrictions such as restricting device function (s) to a certain percentage of usage, to a specific amount of time, to a specific level of capacity (for example, certain energy output level or intensity to limit battery usage, etc.) to a specific amount of dispensed supply, etc. In said embodiments, usage restrictions are instructions executable by device 120 which then cause device 120 to operate according to usage restrictions. Usage restrictions for a particular confirmation message are adjusted by computer 110 so that device usage parameters 120 are still in line with the task needs associated with the confirmation message containing usage restrictions. For example, if a particular device can perform a task function with 70% output, but 100% is desirable because it would complete the task more quickly, the usage restriction will restrict the output to 70% (or another lower value) than 100%), so that it is the maximum output during the task.
    [0080] [0080] In several modalities, the confirmation message can include the minimum readiness attributes of the device for a task, which are stored by the device 120. In the referred modalities, the device 120 is programmed to monitor its various attributes of the device for a task and compare them against one or more stored confirmation messages and, if certain attributes of the device change during use so that a minimum device readiness attribute of a confirmation message for a task occurring subsequently does not is more achieved, device 120 communicates the condition to computer 110.
    [0081] [0081] The scheduled task may also include attributes of expected use with corresponding values for certain device attributes of the various devices, indicating the expected use of a particular resource or provision of a device for the execution of the scheduled task. These values can be used by computer 110 in the subsequent scheduling of tasks as discussed above.
    [0082] [0082] In various modalities, computer 110 can be programmed to detect exceptions, so that a scheduled task cannot make a previously scheduled task impossible, but occurring later. As noted above, the calculated values of the device's expected readiness attribute for one or more devices for a specific task are stored. Thus, computer 110 adjusts one or more anticipated device readiness attribute values for one or more of the tasks previously scheduled, occurring later based on the expected usage attribute values of the task scheduled in step 240 and compares the early device readiness attribute values adjusted to tasks occurring subsequently in relation to the respective minimum readiness attribute values. If the result of the comparison is such that the expected values of the device's expected readiness attribute still meet or exceed the minimum readiness attribute values, there will be no conflict and the task scheduled in step 240 will remain on the schedule. If the adjustment causes the predicted readiness attribute values of the adjusted device to no longer meet the respective minimum readiness attribute values, computer 110 indicates a conflict for the user who submits the current task received in step 210 and removes the scheduled task of the calendar (or, in various ways, does this after step 220 and indicates a failure in the schedule). As with a scheduling failure in step 220, computer 110 can perform an analysis for alternative dates / times for the requested task, so that no conflicts are found for previously scheduled tasks and suggest them to the user.
    [0083] [0083] In a variation of these modalities, certain pre-scheduled tasks can be marked as "essential" or prioritized in another way (such as according to a specific personnel scheduled for the task, a specific device scheduled for the task or others As such, in these modalities, computer 110 is programmed to perform exception analysis for these essential or prioritized tasks to ensure that the task scheduled at the time does not make them impossible to perform and handles this task. occurrence, as discussed above.
    [0084] [0084] Having scheduled the task together with the corresponding device (s), staff, location, etc., for the task in step 240, computer 110 is programmed to, at a designated time of "check-in" before the task indicated by a check-in time attribute for each device in the scheduled task, check the feasibility
    [0085] [0085] The check-in time attribute includes a check-in time attribute value that triggers the check-in process, so that computer 110 checks the viability of one or more devices scheduled for a task at a designated time before the task is scheduled to start. Thus, the value of the check-in time attribute can be a date / time value, a value of one hour before the scheduled start time or another time indication.
    [0086] [0086] In several modalities, a task can have only one or several check-in times, such as one or more days before the scheduled task date, at the beginning of the scheduled task day (for example, at 12:00:00 or another time indicating the start of the day), 4 hours before the start time of a task, 2 hours before the start time of a task, 1 hour before the start time of the task or in other increments of previous times for the scheduled start of the task. In various modes, the check-in time attribute value is the start time of one or more tasks immediately before the scheduled task. The values of the check-in time attributes are, in various modalities, a priori defined by default for each device.
    [0087] [0087] Figure 3 provides an illustrative example of the check-in process, according to the modalities of the object of the present invention.
    [0088] [0088] In step 310, computer 110 calculates the sufficiency information related to a device assigned to a task. Sufficiency information is updated and current sufficiency information for the particular device. To calculate sufficiency information for a device, computer 110 obtains the current device attribute values (from the device database 130 or the ping of the device 120 itself to obtain an updated status for devices capable of such communication) check-in time and,
    [0089] [0089] In step 320, computer 110 determines a device sufficiency status for a task during the task's scheduled time period by comparing the sufficiency information determined in step 310 with the device's minimum readiness attributes for a task. In several modalities, computer 110 determines either a positive sufficiency status (if the sufficiency information continues to reach or exceed the minimum readiness attributes of the device for a task) or a negative sufficiency status (if the sufficiency information now fails to reach or exceed the minimum device readiness attributes for a task).
    [0090] [0090] In various modalities, computer 110 checks the availability of one or more of the personnel assigned to the task at the task's scheduled time in step 321, in response to determining a positive sufficiency status for the device. In some modalities, the verified personnel may be those directly connected to the verified device (for example, operators or technicians required to operate the device for the task). In other modalities, verified personnel may also include other personnel associated with the task (such as "critical" task personnel), even if they are not directly related to the verified device itself.
    [0091] [0091] Having determined a positive sufficiency status, computer 110 proceeds to step 330, where, in the scheduled period of the task, computer 110 communicates with the device to allow execution (via an execution message) one or more functions of device 120. If multiple check-in times are used, computer 110 communicates with device 120 in step 330, after determining a positive sufficiency status at the check-in time closest to scheduled task start time.
    [0092] [0092] The execution message that allows the execution of a device function (s) 120 can be in the form of an unlock message that allows the team to access the functions of the device 120, an activation message that causes the device functions to be activated or an authentication message including login credentials previously provided for device 120 through a confirmation message. This execution message can include new, updated or additional executable usage restrictions that are performed by device 120, as discussed here to restrict the device's functions and outputs accordingly.
    [0093] [0093] If, in step 320, computer 110 determines a negative sufficiency status, computer 110 is programmed to determine a second sufficiency status in step 330a for the device for an alternate time period, and for repeatedly select alternate time periods for the task, until one is found that results in a positive sufficiency status for device 120. Once one is found, the alternative sufficiency status for other devices programmed for the task is calculated and the check for the corresponding personnel is performed and, if the positive sufficiency status results for the alternate period are returned to the other devices and the availability of personnel for the alternate period is confirmed, the computer 110 reschedules the task for the alternate period. At the start time of the alternate time period (or, in various ways, a predefined time before the start time; for example, 10 minutes, 30 minutes or another interval), computer 110 sends the execution message to device 120 to enable the device functions to perform the task in step 330b.
    [0094] [0094] In various modalities, the check-in time can be adjusted from the default based on how close the values of one or more of the anticipated device readiness attributes calculated in step 222 are to yours. respective minimum readiness attribute values of the device (s) for a task. For example, computer 110 determines that an early device readiness attribute value is inserted at a threshold percentage of its respective device minimum readiness attribute value, computer 110 is programmed to adjust the time attribute value. check-in time so that the time between check-in and the start time of the scheduled task is increased by a percentage of the time between the check-in time and the start time of the scheduled task (for example, doubled , increased by 50%, etc.). Thus, computer 110 can, for a situation where the expected readiness of a device for a task is already reasonably close to the minimum requirements, mitigate the greater risk that the use of a device beyond the expected use in tasks prior to the scheduled task make the device unsuitable for the task by checking in with the device over time. Also and / or alternatively, computer 110 may, based on the value (s) of the device's ready attribute attribute (s) within the limit, increase the number of check-in times of so that computer 110 checks in with device 120 more often before the scheduled task starts.
    [0095] [0095] Likewise, the adjustment of the check-in time can be based on the distance between the location of the task immediately before the start of the scheduled task and the location of the scheduled task. For example, if a check-in time is 10 minutes earlier and the location of the scheduled task immediately before a scheduled task is such that the travel time is greater than or equal to 10 minutes, computer 110 is programmed to adjust the time. check-in to account for travel time and a buffer, increasing check-in time by a percentage of travel time (for example, twice travel time, 3x travel time, 50% more than travel time etc.). Thus, the check-in time can be adjusted based on a real-world location.
    [0096] [0096] In several modalities, the check-in time can be adjusted based on a virtual location of the device (for example, a network location). For example, if a device 120 is on a network so that the device's network location increases communication time due to other network factors, the check-in time can be increased accordingly. In another example, if a device 120 is expected to be in an environment where data communication is more likely to be interrupted or completely unavailable, computer 110 can adjust the check-in time to check in with the device before and / or after the device leaves this environment.
    [0097] [0097] In various modalities where multiple check-in times are used, computer 110 can be programmed to adjust subsequent check-in times based on a sufficiency information received at a check-in, by applying the sufficiency information. - science in the same way that the check-in time can be adjusted through the attributes of early readiness at the time of scheduling the task. As such, subsequent check-in times (and, in certain ways, the addition of additional check-in times) can be adjusted based on the updated current information associated with device 120.
    [0098] [0098] In several modalities, the check-in time can be adjusted based on factors such as the availability of alternative devices for a task. In these modalities, computer 110 adjusts travel time as follows:
    [0099] [0099] In said modalities, computer 110 corresponds, in step 221, more than one device 120 to a task attribute in the same way as discussed above, and calculates the suitability for said additional devices 120 for the task scheduled by through the process of steps 222 - 223. Thus, computer 110 selects backup devices 120, in addition to device 120, ultimately scheduled for the task.
    [00100] [00100] If a threshold number of backup devices is reached or exceeded, computer 110 does not adjust the check-in time attribute value. If the threshold amount is not reached, computer 110 is programmed to adjust the check-in time for the selected device by increasing the check-in time. The adjustment can be inversely proportional to the number of backup devices available up to a maximum amount of adjustment (if no backup is found). Thus, as alternatives are lacking, computer 110 increases the check-in time with the selected device 120 to check the continued suitability of the selected device beyond the scheduled start time. Alternatively and / or even, the amount of check-in times can be increased to add additional check-in times based on the number of backup devices. Therefore, if the number of backups reaches the limit, the computer will not add additional scan times. As the number of backups decreases, additional check-in times are added, so that computer 110 checks in with the selected device 120 more frequently as the task start time approaches.
    [00101] [00101] In a variation of the referred modalities, the attributes of the alternatives used to adjust the check-in time include the location of the alternative devices based on the location of the tasks using those devices scheduled more immediately before the start time of the scheduled task. Thus, if one or more of the alternative devices are anticipated to be in a location so that the distance to the location of the scheduled task indicates a travel time that is longer than the default check-in time, the computer 110 increases the check-in time for a task to match or exceed the travel time for one or more of the alternative devices. It should be noted that, in various modalities, computer 110 can be programmed to perform this adjustment even if the anticipated travel time for device 120 currently selected for the scheduled task from its expected previous location does not exceed the check-in time. in.
    [00102] [00102] In various modalities, computer 110 is programmed to adjust the check-in time based on the virtual or network location of one or more of the alternative devices, similar to how computer 110 checks in with the selected device 120 based on virtual or network location as discussed above.
    [00103] [00103] In the referred modalities, computer 110 checks in with the selected device 120 as discussed above and can similarly check in with the alternative devices at each check-in time and, as discussed above, calculate the sufficiency information and determine the sufficiency of the device for each alternative device. Based on the sufficiency information calculated from one or more of the alternative devices, computer 110 is programmed to adjust subsequent check-in times and / or add additional check-in times.
    [00104] [00104] In other modalities, computer 110 first checks in with the selected device 120 and, based on a determination of a negative sufficiency status in step 320, then performs the sufficiency status check for the machines selected alternatives and, based on a positive sufficiency status for an alternative device, schedules the alternative device for a task.
    [00105] [00105] In other modalities, computer 110 does not select alternative devices at the time of creation of the device. Instead, at check-in time and with the determination that the selected device 120 has a negative sufficiency status, computer 110 then selects one or more alternatives based on device attributes and task attributes, and for alternative devices, calculates sufficiency information based on the current values of the attributes and determines a sufficiency status for the alternative device (s) until an alternative device is found having a value positive sufficiency. Computer 110 then schedules the alternate device selected for the task.
    [00106] [00106] In various embodiments, the usage restrictions discussed above generated by computer 110 are based on one or more subsequent tasks scheduled for device 120. Thus, if any exceptions for subsequent tasks are found as discussed above, computer 110 determines whether optimization of device functions 120 is possible in the current task and one or more subsequent tasks to try to resolve the exception. To do so, computer 110 performs a process that obtains the expected usage attribute values for device 120 for a task scheduled in step 240, and performs a hypothetical calculation by adjusting the expected usage attributes of device 120 for the task scheduled in step 240 by reducing one or more of the device attributes associated with a burnout during function (for example,
    [00107] [00107] In various modalities, the exception handling processes are performed by computer 110 for all scheduled tasks whenever a new task is added to the scheduling schedule. In these modalities, computer 110 sends additional confirmation messages for devices 120, including usage restrictions updated as needed to accommodate still scheduled uses. Said additional confirmation messages can be provided to devices 120 on the basis of a push, as new tasks are scheduled and / or at the time of check-in, together with the check-in messages sent by computer 110.
    [00108] [00108] In the modalities discussed above, it is assumed that the device (s) 120 is capable of communicating with computer 110 through the network components through communication methods that can be wired or wireless, long and / or short range and from device to device or through network devices such as routers, etc. Examples of these types of communication include, but are not limited to, USB, HDMI, WiFi, cellular, near field communication, Bluetooth, RFID etc. Thus, in said modalities, devices 120 are able to receive information from computer 110 and send information back to computer 110.
    [00109] [00109] However, in various modalities, it is contemplated that certain devices 120a may not have full communication capabilities (that is, they may only be able to receive data, but not send) or have no ability to communicate. Communication. Such devices may be legacy devices that do not have communication and / or processing resources, or "simple" analog devices that traditionally may not have communication or processing functions (for example, basic stethoscopes, tongue depressors and other "basic" manual functions diagnostic tools or medical treatment). In various modalities, the systems and methods of the object of the invention contemplate the incorporation of the said "dumb" devices, as well as the communication through a proxy.
    [00110] [00110] In the referred modalities, the computer 110 cannot check in with the dumb device directly due to the fact that the device has no capacity to automatically receive a request and respond in the same way. Thus, computer 110 checks in with a dumb device 120a based on a task attribute of a current scheduled task for device 120a or, if there is no scheduled task, with the assigned value.
    [00111] [00111] The check-in process for "dumb" devices 120a is illustrated in Figure 5. To check in with a dumb device 120a, computer 110 first checks (at check-in time) the schedule for the device 120a (either in the central calendar or device profile 121 of device 120a in device database 130) in step 510 to make sure it is currently scheduled to be in use for a scheduled task.
    [00112] [00112] If there is a scheduled task that is using device 120a ("yes" in Fig. 5), computer 110 checks the task location attribute in the scheduled task's calendar entry in step 520 to determine the task location in step 520a. In various modalities, this information is also / instead found in the device programming data in device profile 121 of device 120a and is retrieved from there by computer 110.
    [00113] [00113] Computer 110 then checks the task location for any computing devices having the ability to communicate directly with computer 110 in step 530a, and identifies one or more of the computing devices in a location for the which to send a confirmation request message. These can be other devices 120, or they can be other devices such as computers, cell phones, pagers, tablets, or other computing devices having the ability to communicate in one location.
    [00114] [00114] In various modalities, computer 110 has prior knowledge of the location of certain "fixed" computing devices based on a network map correlated to physical locations, such as inside a facility, hospital, etc. These fixed computing devices are stationary within their physical locations and do not move.
    [00115] [00115] In various modalities in which no fixed computing device is located on site, computer 110 is programmed to locate mobile computing devices (for example, tablets, cell phones, laptops and other mobile computing devices) on-site based on location signals (e.g., GPS, etc.) reported by devices to computer 110, by detecting wireless signals (e.g., accessing a wireless access point, etc.) or by triangulation cellular signals or other wireless signals.
    [00116] [00116] Once computer 110 has located a computing device (such as computing device 150 in Figure 1) at the location 160 in step 530a, computer 110 sends a confirmation request message to the computing device 150 in step 540a for presentation to the user of the computing device 150 at location 160 (illustrated in Figure 1 through the dashed arrow). The presentation can be a visual message to be displayed by a screen on the computing device, an audio message to be emitted from speakers or other audio output from the device, an audio prompt to view a visual message, etc. The confirmation request message is sent in the appropriate mode for presentation, depending on the computing device 150, the output capabilities of the computing device 150 (eg screen, if available; speakers, if available), computing device operating system 150, the application used to display the message (for example, text message, email, a device-specific alert application, etc.) and other device-specific requirements for the device. computing 150 send the request.
    [00117] [00117] The confirmation request message includes a request that the user verifies that the dumb device 120a is in a location 160, and a prompt for a response by the user. The answer can be typing a simple "Y" or "Yes" or "N" / "No", or a device ID number on the device on a keyboard or touch screen input. The answer can be spoken into a microphone on the computing device. The response is then communicated back to computer 110 and is received at step 550a. If the response indicates that device 120a is at a location 160, computer 110 updates the device attribute attribute 133c to device 120a in device database 130 in step 560.
    [00118] [00118] The confirmation request message may include a request for additional information such as supply information or load information, as may be applicable for device 120a and, based on the response, updates other attributes of the device 133 of device profile 121 in device database 130 according to step 560.
    [00119] [00119] If the computing device 150 has a camera, the prompt may include instructions for the user to keep the device identification number or other identifier in front of the camera to capture an image (ie still image or video data ), which is then relayed back to computer 110. Using OCR or other recognition technology, computer 110 checks the device ID provided as corresponding to device 120a and updates the device's location attribute in the database. device 130.
    [00120] [00120] In various modalities, the device 120a can be affixed or printed with a bar code or other machine-readable indications (for example, QR code), which can be scanned and / or captured by image by the computing device (if have a camera and / or a scanner). The scanned information or image is transmitted to the computer 110 by the computing device, and computer 110 checks the information received as corresponding to device 120a and updates device location information 120a in the device database accordingly.
    [00121] [00121] If computer 110 determines that there is no task currently scheduled for device 120a at the time of check-in in step 510 ("no" in Figure 5), computer 110 then checks the location attribute of the device device 120a in the device database 130 at step 520b to obtain the last known location for the device. Having obtained the last known location 160, computer 110 finds one or more computing devices at location 160 at step 530b and sends a confirmation request message to one or more of the computing devices 150 at location 160 at step 540b, as described above in relation to steps 530a, 530b, respectively, and verifies a response in step 550b, as discussed above in relation to 550a. In various ways, computer 110 can check the device location attribute 120a in the device database in the same way if, after consulting the location of a currently scheduled task that includes device 120a, the response sent via of the computing device in the task the location is such that the device 120a is not in the current task location as expected (illustrated by the "no" after step 550a moves to step 520b in Figure 5).
    [00122] [00122] If device 120a is not found, computer 110 will notify the appropriate personnel in step 580, including the scheduler for the task for which check-in is being performed. In various embodiments, computer 110 proceeds to look for alternative periods of time for the task, as discussed above, in response to failure to locate device 120a.
    [00123] [00123] In various modalities, the device database 130 stores a historical record of locations recorded in the past for some or all devices 120a (and also devices 120). In these modalities, if device 120a is not located at the location of its currently programmed task (if applicable) or at the last known location, computer 110 is programmed to obtain one or more of the historical locations in step 570 (preferably starting with the most recent and working backwards in time) and, for each of these historical sites, repeating steps 530b - 550b until the device is found. If device 120a is not found after exhausting all historical sites stored in device profile 121 for the device (or after a predetermined set of attempts), computer 110 performs step 580.
    [00124] [00124] It is contemplated that the processes discussed with dumb devices 120a can also be applied if a device 120 that has the appropriate communication and processing capabilities cannot be located or reached by computer 110 at check-in (for example, due to a power failure or lack of battery power, having been disconnected by a user, a problem with the communications interface on device 120, a problem with the network that prevents communication, etc.).
    [00125] [00125] Thus, the systems and methods of the object of the invention allow the integration of disconnected devices in a networked device management and programming system, thus eliminating the limitations of previous programming systems that would not be able to deal with these devices and require separate manual management of the device.
    [00126] [00126] In various modalities, the device attributes and the task attributes mentioned here can be categorized as
    [00127] [00127] Examples of non-unique attributes for a task may include, but are not limited to, a person with a set of non-unique attributes, a resource with a set of non-unique attributes, a period of time, a subsequent task and / or a preparatory task. Examples of attributes not unique to a person may include, but are not limited to, a corporate title, a skill, a skill level, a capacity, a resource preference, a task preference, a coworker preference, and / or an available period of time. Examples of non-unique attributes for non-human resources (for example, materials, consumables, fixed equipment, mobile tools, rooms, buildings, computers, projectors, telephones) may include, but are not limited to, quantity, quality, capacity , availability, type, cost, location and / or life cycle.
    [00128] [00128] As used here, and unless the context dictates otherwise, the term "coupled to" must include both direct coupling (in which two elements coupled together) and indirect (in which at least least one additional element is located between the two elements). Therefore, the terms "coupled to" and "coupled with" are used interchangeably.
    [00129] [00129] It should be evident to those skilled in the art that many other modifications besides those already described are possible without departing from the concepts of the invention presented here. The object of the invention, therefore, should not be restricted, except in the spirit of the appended claims. In addition, when interpreting both the descriptive report and the claims, all terms must be interpreted in the broadest possible way, consistent with the context. In particular, the terms "comprises" and "comprising" should be interpreted as referring to elements, components or steps in a non-exclusive manner, indicating that the elements, components or steps mentioned may be present, or used, or combined with other elements, components or steps that are not expressly referenced. Where specification claims refer to at least one of the items selected from the group consisting of A, B, C .... and N, the text should be interpreted as requiring only one member of the group, not A plus N , or B plus N, etc.
    权利要求:
    Claims (17)
    [1]
    1. Method of ensuring the viability of a machine for a scheduled task characterized by the fact that it comprises: receiving, by a computing device, a request for a task, the request including a plurality of pairs of task attributes / values that correspond for task, task attribute / value pairs including a desired time period attribute / value pair that corresponds to a time period requested for a task; select, by the computing device, a person for the task based on the pairs of attribute / task values and attribute / value pairs of each of a plurality of people, including the attribute / value pair of time period wanted; select, by the computing device, a machine for a task based on the pairs of attributes / values of the task and pairs of attributes / values of each of a plurality of machines, including the attribute / value pair of time period wanted; obtain, by the computing device and at the check-in time before a requested period of time, sufficiency information that corresponds to the machine; in response to obtaining the sufficiency information, determining, by the computing device, a sufficiency status for the machine for the task during the requested time period be as a positive sufficiency status and a negative sufficiency status. va, based on sufficiency information obtained; and within a requested time period, communicate, via the computing device, with the machine to perform a function of the corresponding machine in response to determining the positive sufficiency status for a machine.
    [2]
    2. Method, according to claim 1, characterized by the fact that it still comprises, in response to determining a positive sufficiency status for the machine, verifying an availability of the person selected for the task in the desired period of time - of.
    [3]
    3. Method, according to claim 1, characterized by the fact that it still comprises, in response to selecting a machine: selecting, by the computing device, at least a second machine for the task based on the pairs of attributes / task values and attribute / value pairs for each of the machines, including the desired attribute / time period value pair; determine, by the computing device, a projected set of attribute / value pairs for each of at least one second machine based on at least one corresponding set of task scheduling attribute / value pairs for each one of at least one second machine, the at least one set of task scheduling attribute / value pairs that corresponds to at least one previous task scheduled for at least one corresponding second machine before a requested time period; and adjust the check-in time based on the projected set of attribute / value pairs.
    [4]
    4. Method according to claim 3, characterized by the fact that the task scheduling attribute / value pairs include a location attribute / value pair that corresponds to a location of the corresponding previous scheduled task.
    [5]
    5. Method, according to claim 4, characterized by the fact that the location attribute / value pair corresponds to at least one of a real-world location and a virtual location.
    [6]
    6. Method, according to claim 1, characterized by the fact that it still comprises, in response to selecting a machine: selecting, by the computing device, at least one second potential machine for the task based on the pairs of attributes / values the task and the attribute / value pairs for each of the machines, including the desired time period attribute / value pair; determine, by the computing device, the number of selected machines; and adjust, by the computing device, the check-in time based on the number of selected machines.
    [7]
    7. Method, according to claim 1, characterized by the fact that the check-in time comprises a stored time parameter that corresponds to a predefined time period before the beginning of the requested time period.
    [8]
    8. Method, according to claim 1, characterized by the fact that it still comprises: in response to determining a negative sufficiency status for the machine, selecting a second machine for the task based on the attribute / value pairs of the task and attribute / value pairs for each of the machines, including the desired time period attribute / value pair; obtain sufficiency information corresponding to the second machine; in response to obtaining the sufficiency information, determine a second sufficiency status for the machine for the task for the desired period of time; and determining a positive fill status for the second machine; and within the desired time period, communicating with the second machine to perform the function of the second machine in response to determining a positive sufficiency status for the second machine.
    [9]
    9. Method, according to claim 1, characterized by the fact that it still comprises: in response to determining a negative sufficiency status for the machine for the desired period of time, determining an alternative sufficiency status for the machine for the task for a desired second period of time is either an alternative status of positive sufficiency and an alternative status of negative sufficiency, based on the sufficiency information obtained; and within the desired second time period, communicate with the machine to perform the machine's function in response to determining an alternate positive sufficiency status for the machine.
    [10]
    10. Method, according to claim 1, characterized by the fact that the obtaining step is performed after the machine selection.
    [11]
    11. Method, according to claim 1, characterized by the fact that it still comprises sending, through the compute device, a notification to the selected person that the task has been scheduled and that the person has to help carry out the task during the desired period of time.
    [12]
    12. Method, according to claim 1, characterized by the fact that it still comprises sending, through the compute device, a confirmation to the task machine.
    [13]
    13. Method, according to claim 1, characterized by the fact that the machine comprises at least one of computing devices, general medical devices, special tools
    environmental controls, medical scanning equipment, diagnostic equipment, patient monitoring equipment, surgical instruments, patient beds, patient wheelchairs, computing equipment, anesthesia equipment, room environmental controls, and specialized medical devices.
    [14]
    14. Method, according to claim 1, characterized by the fact that the attributes of the machine's attribute / value pairs include unique machine attributes and non-unique machine attributes.
    [15]
    15. Method according to claim 1, characterized by the fact that the attributes of task attribute / value pairs include unique task attributes and non-unique task attributes.
    [16]
    16. Method, according to claim 1, characterized by the fact that the step of communicating is performed directly with the machine.
    [17]
    17. Method, according to claim 1, characterized by the fact that the step of communicating between the computing device is performed through a proxy.
    38 Ss a & ã a = | Ss 2 A 2 & 2 & ô o ô se We s Ss ls 2 | 9 =). 83 | 85 gglEsill824 0 o gen sl Es fas ETSBsS | ions 22 888 - = to EI 2 if NS = | mA uu = À = | = H 811.8 3 of these are Ss ESEC 235 22/82 2 DH068 SS gg5886SS
    AND
    s
    The lala | S 8222 2 oo Tal E | E 83883 o o s $ 2/0 | : ij::: a: i o ie 328 ã:; o ga =: imo E8 mol: 18 25 Ê 'S&S 82 THERE IS 1 1 Ss E â' ig | os i iG i 8:
    Step 210 - Receive task request Step 220 Step 222 - Calculate early device readiness attribute Step 223 - Compare with minimum device readiness attribute Step 230 - Select staff Step 240 - Scheduled task
    类似技术:
    公开号 | 公开日 | 专利标题
    BR112020003112A2|2020-08-11|systems and methods of ensuring and maintaining the viability of equipment for a task
    US11044221B2|2021-06-22|Integration of devices through a social networking platform
    US11080367B2|2021-08-03|System-wide probabilistic alerting and activation
    US20200020442A1|2020-01-16|System for dynamic location-aware patient care process controls and dynamic location-aware tracking
    JP2017512614A|2017-05-25|Managing health expertise and resource allocation
    US20140108033A1|2014-04-17|Healthcare enterprise simulation model initialized with snapshot data
    US10262110B2|2019-04-16|Systems and methods for managing patient devices
    US10789335B2|2020-09-29|Remote diagnosis management system and method for operating the same
    KR102020284B1|2019-09-11|Healthcare data providing server, providing method and program
    US20150178461A1|2015-06-25|Group posture health risk management
    JP2017527936A|2017-09-21|Capture and manage health management information
    JP2009086766A|2009-04-23|Medical network system, and medical examination request management device and method
    KR20220020442A|2022-02-18|Systems and methods of ensuring and maintaining equipment viability for a task
    US20150154530A1|2015-06-04|Method and computer program product for task management on late clinical information
    US11170875B2|2021-11-09|Methods and apparatus for data-driven monitoring
    US20190362837A1|2019-11-28|Systems and methods for efficiently managing hospital operating rooms
    US11107590B2|2021-08-31|Cloud-to-local, local-to-cloud switching and synchronization of medical images and data with advanced data retrieval
    US20180144097A1|2018-05-24|Method and System for Tag-Based Task Creation, Monitoring and Escalation
    JP2019537127A|2019-12-19|Capture and use of clinical path resource usage
    WO2018141012A1|2018-08-09|Workplace task management system and process
    JP2015092323A|2015-05-14|Clinical path management device
    TW201510869A|2015-03-16|Virtual client load control system and virtual client load control method
    同族专利:
    公开号 | 公开日
    EP3669309A1|2020-06-24|
    AU2018318694A1|2020-03-05|
    JP6964906B2|2021-11-10|
    CN111213164A|2020-05-29|
    KR102361481B1|2022-02-09|
    WO2019035934A1|2019-02-21|
    US10163065B1|2018-12-25|
    AU2021290327A1|2022-02-03|
    US20190130339A1|2019-05-02|
    JP2020532027A|2020-11-05|
    KR20200033353A|2020-03-27|
    US11093872B2|2021-08-17|
    US20210374651A1|2021-12-02|
    EP3669309A4|2021-04-21|
    AU2018318694B2|2021-10-14|
    CA3073039A1|2019-02-21|
    引用文献:
    公开号 | 申请日 | 公开日 | 申请人 | 专利标题
    JP3067882B2|1992-01-20|2000-07-24|株式会社島津製作所|Reservation management device for medical examination equipment|
    US5673034A|1993-10-12|1997-09-30|Saliga; Thomas V.|Security system comprising three apparatuses sharing a time-varying code|
    US6049742A|1997-09-26|2000-04-11|International Business Machines Corporation|Projected supply planning matching assets with demand in microelectronics manufacturing|
    US6157916A|1998-06-17|2000-12-05|The Hoffman Group|Method and apparatus to control the operating speed of a papermaking facility|
    JP3288348B2|1999-08-23|2002-06-04|健 長谷川|Inspection appointment system and inspection appointment method with built-in inspection date automatic determination function|
    US7587329B2|2000-06-02|2009-09-08|Drason Consulting Services, Llc|Method and system for optimizing employee scheduling in a patient care environment|
    US8706542B2|2000-12-18|2014-04-22|Apple Inc.|Allocation of location-based orders to mobile agents|
    US7502747B1|2001-11-29|2009-03-10|Microsoft Corporation|Automated job scheduling based on resource availability|
    US7516455B2|2003-09-05|2009-04-07|Microsoft Corporation|Probabilistic scheduling|
    US6983188B2|2004-04-16|2006-01-03|Hewlett-Packard Development Company, L.P.|Scheduling system|
    JP2006209288A|2005-01-26|2006-08-10|Fuji Xerox Co Ltd|Information processor, information processing method, and computer program|
    US8229761B2|2005-02-25|2012-07-24|Virtual Radiologic Corporation|Enhanced multiple resource planning and forecasting|
    US20090036750A1|2007-05-25|2009-02-05|The Charles Stark Draper Laboratory, Inc.|Integration and control of medical devices in a clinical environment|
    US20090199192A1|2008-02-05|2009-08-06|Robert Laithwaite|Resource scheduling apparatus and method|
    US20090315753A1|2008-06-19|2009-12-24|Contec Llc|Apparatus and method for managing memory of a digital video recorder|
    FR2956501B1|2010-02-17|2012-03-09|Evidian|METHOD FOR REMOTELY LOCKING / UNLOCKING A MACHINE|
    US8560368B1|2011-11-18|2013-10-15|Lockheed Martin Corporation|Automated constraint-based scheduling using condition-based maintenance|
    US20130339969A1|2012-06-19|2013-12-19|Nmetric, Llc|Scheduling and Decision System|
    KR101482520B1|2013-04-03|2015-01-16|주식회사 인피니트헬스케어|Medical workflow-based adaptive display system and method|
    US20160379175A1|2015-06-23|2016-12-29|Mayukh Bhattacharya|System and Method for Automated Optimized Personal Task Scheduling and Targeted Advertising|
    US10163065B1|2017-08-16|2018-12-25|Nmetric, Llc|Systems and methods of ensuring and maintaining equipment viability for a task|US20070084897A1|2003-05-20|2007-04-19|Shelton Frederick E Iv|Articulating surgical stapling instrument incorporating a two-piece e-beam firing mechanism|
    US8215531B2|2004-07-28|2012-07-10|Ethicon Endo-Surgery, Inc.|Surgical stapling instrument having a medical substance dispenser|
    US7669746B2|2005-08-31|2010-03-02|Ethicon Endo-Surgery, Inc.|Staple cartridges for forming staples having differing formed staple heights|
    US9237891B2|2005-08-31|2016-01-19|Ethicon Endo-Surgery, Inc.|Robotically-controlled surgical stapling devices that produce formed staples having different lengths|
    US11246590B2|2005-08-31|2022-02-15|Cilag Gmbh International|Staple cartridge including staple drivers having different unfired heights|
    US20070106317A1|2005-11-09|2007-05-10|Shelton Frederick E Iv|Hydraulically and electrically actuated articulation joints for surgical instruments|
    US11207064B2|2011-05-27|2021-12-28|Cilag Gmbh International|Automated end effector component reloading system for use with a robotic system|
    US11224427B2|2006-01-31|2022-01-18|Cilag Gmbh International|Surgical stapling system including a console and retraction assembly|
    US7845537B2|2006-01-31|2010-12-07|Ethicon Endo-Surgery, Inc.|Surgical instrument having recording capabilities|
    US8186555B2|2006-01-31|2012-05-29|Ethicon Endo-Surgery, Inc.|Motor-driven surgical cutting and fastening instrument with mechanical closure system|
    US8684253B2|2007-01-10|2014-04-01|Ethicon Endo-Surgery, Inc.|Surgical instrument with wireless communication between a control unit of a robotic system and remote sensor|
    US11039836B2|2007-01-11|2021-06-22|Cilag Gmbh International|Staple cartridge for use with a surgical stapling instrument|
    US8931682B2|2007-06-04|2015-01-13|Ethicon Endo-Surgery, Inc.|Robotically-controlled shaft based rotary drive systems for surgical instruments|
    US7753245B2|2007-06-22|2010-07-13|Ethicon Endo-Surgery, Inc.|Surgical stapling instruments|
    US8573465B2|2008-02-14|2013-11-05|Ethicon Endo-Surgery, Inc.|Robotically-controlled surgical end effector system with rotary actuated closure systems|
    US9585657B2|2008-02-15|2017-03-07|Ethicon Endo-Surgery, Llc|Actuator for releasing a layer of material from a surgical end effector|
    US8210411B2|2008-09-23|2012-07-03|Ethicon Endo-Surgery, Inc.|Motor-driven surgical cutting instrument|
    US9386983B2|2008-09-23|2016-07-12|Ethicon Endo-Surgery, Llc|Robotically-controlled motorized surgical instrument|
    US8608045B2|2008-10-10|2013-12-17|Ethicon Endo-Sugery, Inc.|Powered surgical cutting and stapling apparatus with manually retractable firing system|
    US8517239B2|2009-02-05|2013-08-27|Ethicon Endo-Surgery, Inc.|Surgical stapling instrument comprising a magnetic element driver|
    US20110024477A1|2009-02-06|2011-02-03|Hall Steven G|Driven Surgical Stapler Improvements|
    US10945731B2|2010-09-30|2021-03-16|Ethicon Llc|Tissue thickness compensator comprising controlled release and expansion|
    US9861361B2|2010-09-30|2018-01-09|Ethicon Llc|Releasable tissue thickness compensator and fastener cartridge having the same|
    JP6305979B2|2012-03-28|2018-04-04|エシコン・エンド−サージェリィ・インコーポレイテッドＥｔｈｉｃｏｎ Ｅｎｄｏ−Ｓｕｒｇｅｒｙ，Ｉｎｃ．|Tissue thickness compensator with multiple layers|
    JP6224070B2|2012-03-28|2017-11-01|エシコン・エンド−サージェリィ・インコーポレイテッドＥｔｈｉｃｏｎ Ｅｎｄｏ−Ｓｕｒｇｅｒｙ，Ｉｎｃ．|Retainer assembly including tissue thickness compensator|
    US9072535B2|2011-05-27|2015-07-07|Ethicon Endo-Surgery, Inc.|Surgical stapling instruments with rotatable staple deployment arrangements|
    US9101358B2|2012-06-15|2015-08-11|Ethicon Endo-Surgery, Inc.|Articulatable surgical instrument comprising a firing drive|
    US20140001231A1|2012-06-28|2014-01-02|Ethicon Endo-Surgery, Inc.|Firing system lockout arrangements for surgical instruments|
    US9364230B2|2012-06-28|2016-06-14|Ethicon Endo-Surgery, Llc|Surgical stapling instruments with rotary joint assemblies|
    RU2636861C2|2012-06-28|2017-11-28|Этикон Эндо-Серджери, Инк.|Blocking of empty cassette with clips|
    US11197671B2|2012-06-28|2021-12-14|Cilag Gmbh International|Stapling assembly comprising a lockout|
    RU2669463C2|2013-03-01|2018-10-11|Этикон Эндо-Серджери, Инк.|Surgical instrument with soft stop|
    US9629629B2|2013-03-14|2017-04-25|Ethicon Endo-Surgey, LLC|Control systems for surgical instruments|
    MX369362B|2013-08-23|2019-11-06|Ethicon Endo Surgery Llc|Firing member retraction devices for powered surgical instruments.|
    US20150053746A1|2013-08-23|2015-02-26|Ethicon Endo-Surgery, Inc.|Torque optimization for surgical instruments|
    US9962161B2|2014-02-12|2018-05-08|Ethicon Llc|Deliverable surgical instrument|
    US11259799B2|2014-03-26|2022-03-01|Cilag Gmbh International|Interface systems for use with surgical instruments|
    JP6612256B2|2014-04-16|2019-11-27|エシコンエルエルシー|Fastener cartridge with non-uniform fastener|
    BR112017004361A2|2014-09-05|2017-12-05|Ethicon Llc|medical overcurrent modular power supply|
    US9757128B2|2014-09-05|2017-09-12|Ethicon Llc|Multiple sensors with one sensor affecting a second sensor's output or interpretation|
    BR112017005981A2|2014-09-26|2017-12-19|Ethicon Llc|surgical staplers and ancillary materials|
    US9924944B2|2014-10-16|2018-03-27|Ethicon Llc|Staple cartridge comprising an adjunct material|
    US11141153B2|2014-10-29|2021-10-12|Cilag Gmbh International|Staple cartridges comprising driver arrangements|
    US9968355B2|2014-12-18|2018-05-15|Ethicon Llc|Surgical instruments with articulatable end effectors and improved firing beam support arrangements|
    US11154301B2|2015-02-27|2021-10-26|Cilag Gmbh International|Modular stapling assembly|
    US10245033B2|2015-03-06|2019-04-02|Ethicon Llc|Surgical instrument comprising a lockable battery housing|
    US10548504B2|2015-03-06|2020-02-04|Ethicon Llc|Overlaid multi sensor radio frequencyelectrode system to measure tissue compression|
    US9993248B2|2015-03-06|2018-06-12|Ethicon Endo-Surgery, Llc|Smart sensors with local signal processing|
    US11058425B2|2015-08-17|2021-07-13|Ethicon Llc|Implantable layers for a surgical instrument|
    US10238386B2|2015-09-23|2019-03-26|Ethicon Llc|Surgical stapler having motor control based on an electrical parameter related to a motor current|
    US10299878B2|2015-09-25|2019-05-28|Ethicon Llc|Implantable adjunct systems for determining adjunct skew|
    US10980539B2|2015-09-30|2021-04-20|Ethicon Llc|Implantable adjunct comprising bonded layers|
    US20170109684A1|2015-10-14|2017-04-20|Schlumberger Technology Corporation|Assignment and Management of Tasks to Perform Wellsite Operations|
    US10763953B2|2015-11-11|2020-09-01|Schlumberger Technology Corporation|Aerial-based communication system|
    US10368865B2|2015-12-30|2019-08-06|Ethicon Llc|Mechanisms for compensating for drivetrain failure in powered surgical instruments|
    US10265068B2|2015-12-30|2019-04-23|Ethicon Llc|Surgical instruments with separable motors and motor control circuits|
    US10292704B2|2015-12-30|2019-05-21|Ethicon Llc|Mechanisms for compensating for battery pack failure in powered surgical instruments|
    US11213293B2|2016-02-09|2022-01-04|Cilag Gmbh International|Articulatable surgical instruments with single articulation link arrangements|
    US11224426B2|2016-02-12|2022-01-18|Cilag Gmbh International|Mechanisms for compensating for drivetrain failure in powered surgical instruments|
    US11179150B2|2016-04-15|2021-11-23|Cilag Gmbh International|Systems and methods for controlling a surgical stapling and cutting instrument|
    US10456137B2|2016-04-15|2019-10-29|Ethicon Llc|Staple formation detection mechanisms|
    US10357247B2|2016-04-15|2019-07-23|Ethicon Llc|Surgical instrument with multiple program responses during a firing motion|
    US10335145B2|2016-04-15|2019-07-02|Ethicon Llc|Modular surgical instrument with configurable operating mode|
    US10368867B2|2016-04-18|2019-08-06|Ethicon Llc|Surgical instrument comprising a lockout|
    US20180168618A1|2016-12-21|2018-06-21|Ethicon Endo-Surgery, Llc|Surgical stapling systems|
    JP2020501779A|2016-12-21|2020-01-23|エシコン エルエルシーＥｔｈｉｃｏｎ ＬＬＣ|Surgical stapling system|
    US11179155B2|2016-12-21|2021-11-23|Cilag Gmbh International|Anvil arrangements for surgical staplers|
    US10675026B2|2016-12-21|2020-06-09|Ethicon Llc|Methods of stapling tissue|
    US11134942B2|2016-12-21|2021-10-05|Cilag Gmbh International|Surgical stapling instruments and staple-forming anvils|
    US11191539B2|2016-12-21|2021-12-07|Cilag Gmbh International|Shaft assembly comprising a manually-operable retraction system for use with a motorized surgical instrument system|
    US11160551B2|2016-12-21|2021-11-02|Cilag Gmbh International|Articulatable surgical stapling instruments|
    US10307170B2|2017-06-20|2019-06-04|Ethicon Llc|Method for closed loop control of motor velocity of a surgical stapling and cutting instrument|
    US11071554B2|2017-06-20|2021-07-27|Cilag Gmbh International|Closed loop feedback control of motor velocity of a surgical stapling and cutting instrument based on magnitude of velocity error measurements|
    US11090046B2|2017-06-20|2021-08-17|Cilag Gmbh International|Systems and methods for controlling displacement member motion of a surgical stapling and cutting instrument|
    US11141154B2|2017-06-27|2021-10-12|Cilag Gmbh International|Surgical end effectors and anvils|
    US11266405B2|2017-06-27|2022-03-08|Cilag Gmbh International|Surgical anvil manufacturing methods|
    US11259805B2|2017-06-28|2022-03-01|Cilag Gmbh International|Surgical instrument comprising firing member supports|
    US11246592B2|2017-06-28|2022-02-15|Cilag Gmbh International|Surgical instrument comprising an articulation system lockable to a frame|
    US10639037B2|2017-06-28|2020-05-05|Ethicon Llc|Surgical instrument with axially movable closure member|
    US20190000474A1|2017-06-28|2019-01-03|Ethicon Llc|Surgical instrument comprising selectively actuatable rotatable couplers|
    US10163065B1|2017-08-16|2018-12-25|Nmetric, Llc|Systems and methods of ensuring and maintaining equipment viability for a task|
    US11090075B2|2017-10-30|2021-08-17|Cilag Gmbh International|Articulation features for surgical end effector|
    US11134944B2|2017-10-30|2021-10-05|Cilag Gmbh International|Surgical stapler knife motion controls|
    US11071543B2|2017-12-15|2021-07-27|Cilag Gmbh International|Surgical end effectors with clamping assemblies configured to increase jaw aperture ranges|
    US11197670B2|2017-12-15|2021-12-14|Cilag Gmbh International|Surgical end effectors with pivotal jaws configured to touch at their respective distal ends when fully closed|
    US11020112B2|2017-12-19|2021-06-01|Ethicon Llc|Surgical tools configured for interchangeable use with different controller interfaces|
    US11076853B2|2017-12-21|2021-08-03|Cilag Gmbh International|Systems and methods of displaying a knife position during transection for a surgical instrument|
    US10743868B2|2017-12-21|2020-08-18|Ethicon Llc|Surgical instrument comprising a pivotable distal head|
    US11129680B2|2017-12-21|2021-09-28|Cilag Gmbh International|Surgical instrument comprising a projector|
    US11039834B2|2018-08-20|2021-06-22|Cilag Gmbh International|Surgical stapler anvils with staple directing protrusions and tissue stability features|
    US11045192B2|2018-08-20|2021-06-29|Cilag Gmbh International|Fabricating techniques for surgical stapler anvils|
    US11207065B2|2018-08-20|2021-12-28|Cilag Gmbh International|Method for fabricating surgical stapler anvils|
    USD914878S1|2018-08-20|2021-03-30|Ethicon Llc|Surgical instrument anvil|
    US11083458B2|2018-08-20|2021-08-10|Cilag Gmbh International|Powered surgical instruments with clutching arrangements to convert linear drive motions to rotary drive motions|
    US11253256B2|2018-08-20|2022-02-22|Cilag Gmbh International|Articulatable motor powered surgical instruments with dedicated articulation motor arrangements|
    US11172929B2|2019-03-25|2021-11-16|Cilag Gmbh International|Articulation drive arrangements for surgical systems|
    US11147551B2|2019-03-25|2021-10-19|Cilag Gmbh International|Firing drive arrangements for surgical systems|
    US11147553B2|2019-03-25|2021-10-19|Cilag Gmbh International|Firing drive arrangements for surgical systems|
    US11253254B2|2019-04-30|2022-02-22|Cilag Gmbh International|Shaft rotation actuator on a surgical instrument|
    US11051807B2|2019-06-28|2021-07-06|Cilag Gmbh International|Packaging assembly including a particulate trap|
    US11219455B2|2019-06-28|2022-01-11|Cilag Gmbh International|Surgical instrument including a lockout key|
    US11259803B2|2019-06-28|2022-03-01|Cilag Gmbh International|Surgical stapling system having an information encryption protocol|
    US11241235B2|2019-06-28|2022-02-08|Cilag Gmbh International|Method of using multiple RFID chips with a surgical assembly|
    US11246678B2|2019-06-28|2022-02-15|Cilag Gmbh International|Surgical stapling system having a frangible RFID tag|
    US11224497B2|2019-06-28|2022-01-18|Cilag Gmbh International|Surgical systems with multiple RFID tags|
    US11234698B2|2019-12-19|2022-02-01|Cilag Gmbh International|Stapling system comprising a clamp lockout and a firing lockout|
    法律状态:
    2020-09-08| B25G| Requested change of headquarter approved|Owner name: NMETRIC, LLC (US) |
    2021-11-03| B350| Update of information on the portal [chapter 15.35 patent gazette]|
    优先权:
    申请号 | 申请日 | 专利标题
    US15/679,039|2017-08-16|
    US15/679,039|US10163065B1|2017-08-16|2017-08-16|Systems and methods of ensuring and maintaining equipment viability for a task|
    PCT/US2018/000207|WO2019035934A1|2017-08-16|2018-08-16|Systems and methods of ensuring and maintaining equipment viability for a task|
    [返回顶部]